Update version to 2.2.16 across project files#519
Conversation
- Incremented PraisonAI version from 2.2.15 to 2.2.16 in `pyproject.toml`, `uv.lock`, and all relevant Dockerfiles for consistency. - Updated dependency version for `praisonaiagents` from 0.0.88 to 0.0.89. - Ensured minimal changes to existing code while maintaining versioning accuracy across the project.
✅ Deploy Preview for praisonai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Rate limit exceeded@MervinPraison has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 54 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (11)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @MervinPraison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
Hello team, gemini-code-assist here to provide a summary of this pull request. This PR primarily focuses on updating version numbers across the project to reflect a new release. Specifically, it increments the main PraisonAI version to 2.2.16 and updates the dependency on praisonaiagents to version 0.0.89. These changes are propagated through various configuration files, Dockerfiles, and documentation snippets to ensure consistency.
Highlights
- PraisonAI Version Bump: The main project version for PraisonAI has been updated from
2.2.15to2.2.16inpyproject.tomlanduv.lock. - praisonaiagents Dependency Update: The required version for the
praisonaiagentsdependency has been updated from>=0.0.88to>=0.0.89inpyproject.tomlanduv.lock. Thepraisonaiagentsproject itself also has its version updated to0.0.89in itspyproject.tomlanduv.lock. - Dockerfile and Documentation Updates: Various Dockerfiles (
docker/Dockerfile,docker/Dockerfile.chat,docker/Dockerfile.dev,docker/Dockerfile.ui) and documentation files (docs/api/praisonai/deploy.html,docs/developers/local-development.mdx,docs/ui/chat.mdx,docs/ui/code.mdx) have been updated to reference the newpraisonai==2.2.16version inpip installcommands or code snippets. - Deployment Script Update: The
praisonai/deploy.pyscript, which generates a Dockerfile, has been updated to include the newpraisonai==2.2.16version in the generatedpip installcommand string.
Changelog
Click here to see the changelog
- docker/Dockerfile
- Updated
praisonaiversion from2.2.15to2.2.16in theRUN pip installcommand (line 4).
- Updated
- docker/Dockerfile.chat
- Updated
praisonaiversion from2.2.15to2.2.16in theRUN pip installcommand (line 16).
- Updated
- docker/Dockerfile.dev
- Updated
praisonaiversion from2.2.15to2.2.16in theRUN pip installcommand (line 18).
- Updated
- docker/Dockerfile.ui
- Updated
praisonaiversion from2.2.15to2.2.16in theRUN pip installcommand (line 16).
- Updated
- docs/api/praisonai/deploy.html
- Updated
praisonaiversion from2.2.15to2.2.16in the Dockerfile code snippet within the HTML (line 113).
- Updated
- docs/developers/local-development.mdx
- Updated
praisonaiversion from2.2.15to2.2.16in the Dockerfile code snippet within the markdown (line 30).
- Updated
- docs/ui/chat.mdx
- Updated
praisonaiversion from2.2.15to2.2.16in the Dockerfile code snippet within the markdown (line 158).
- Updated
- docs/ui/code.mdx
- Updated
praisonaiversion from2.2.15to2.2.16in the Dockerfile code snippet within the markdown (line 211).
- Updated
- praisonai/deploy.py
- Updated
praisonaiversion from2.2.15to2.2.16in the string literal used to generate the Dockerfile content (line 59).
- Updated
- pyproject.toml
- Updated
project.versionfrom2.2.15to2.2.16(line 3). - Updated
dependencies.praisonaiagentsversion specifier from>=0.0.88to>=0.0.89(line 15). - Updated
tool.poetry.versionfrom2.2.15to2.2.16(line 92). - Updated
tool.poetry.dependencies.praisonaiagentsversion specifier from>=0.0.88to>=0.0.89(line 110).
- Updated
- src/praisonai-agents/pyproject.toml
- Updated
project.versionforpraisonaiagentsfrom0.0.88to0.0.89(line 7).
- Updated
- src/praisonai-agents/uv.lock
- Updated the locked version of
praisonaiagentsfrom0.0.88to0.0.89(line 1460). - Updated the sdist and wheel URLs, hashes, and sizes for
praisonaiagents(lines 3824-3826).
- Updated the locked version of
- uv.lock
- Updated the locked version of
praisonaifrom2.2.15to2.2.16(line 3617). - Updated the required version specifier for
praisonaiagentsfrom>=0.0.88to>=0.0.89(line 3759). - Updated the locked version of
praisonaiagentsfrom0.0.88to0.0.89(line 3816). - Updated the sdist and wheel URLs, hashes, and sizes for
praisonaiagents(lines 3824-3826).
- Updated the locked version of
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Version bumps appear,
Numbers change throughout the code,
Release is now near.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request aims to update the PraisonAI version to 2.2.16 and the praisonaiagents dependency to 0.0.89. The changes made within the modified files (Dockerfiles, pyproject.toml, uv.lock, and documentation) appear to be correct and consistently apply the new version numbers.
However, for comprehensive versioning accuracy across the project, there are a couple of important points to consider:
- Homebrew Formula (
praisonai.rb): Thepraisonai.rbfile in the repository root still refers to version2.1.1. If this Homebrew formula is intended for users to install PraisonAI, it critically needs to be updated to2.2.16to ensure users receive the correct version. This is the primary concern for this review. - Internal Version File (
praisonai/version.py): The filepraisonai/version.pydefines__version__ = "0.0.1". This is inconsistent with the main project version2.2.16(defined inpyproject.toml). To avoid confusion and ensure a single source of truth for the version, this file should either be updated, aligned with the main version, or removed if it's obsolete.
While the changes in this PR are accurate for the files touched, addressing the Homebrew formula is important for the release's consistency.
Summary of Findings
- Homebrew formula out of date: The Homebrew formula
praisonai.rb(located in the project root) still points to version 2.1.1 (url "https://github.com/MervinPraison/PraisonAI/archive/refs/tags/2.1.1.tar.gz"). If this formula is actively maintained and used for distribution, it should be updated to reflect the new version 2.2.16. Not updating this could lead to users installing an outdated version via Homebrew. This is considered a high-severity issue concerning the completeness of the version update across all distribution channels. (No direct file comment aspraisonai.rbwas not part of the diff.) - Inconsistent version in
praisonai/version.py: The filepraisonai/version.pycontains__version__ = "0.0.1". This conflicts with the project version2.2.16specified inpyproject.toml. This discrepancy can lead to confusion or errors if different parts of the system try to read the version from different sources. It's recommended to reconcile this, perhaps by removingpraisonai/version.pyifpyproject.tomlis the single source of truth, or by ensuring it's updated consistently. This is a medium-severity maintainability concern. (No direct file comment aspraisonai/version.pywas not part of the diff.) - Minor Dockerfile pip install style consistency: There's a minor inconsistency in how
praisonaiis specified inpip installcommands within Dockerfiles. For example,docker/Dockerfileusespraisonai==2.2.16(no quotes), whiledocker/Dockerfile.chat(and others) use"praisonai==2.2.16"(with quotes). Whilepiphandles both forms correctly, adopting a consistent style (either always with quotes or always without for package==version specifications) can improve readability. This is a low-severity stylistic issue. (No review comment added due to severity settings.)
Merge Readiness
The changes within this pull request (updates to versions in pyproject.toml, uv.lock, Dockerfiles, and documentation files) are correctly implemented. However, before merging, I strongly recommend addressing the outdated Homebrew formula (praisonai.rb) to ensure version consistency across all distribution methods. The potential inconsistency with praisonai/version.py should also be reviewed. As a reviewer, I am not authorized to approve pull requests, but I advise that these points, particularly the Homebrew formula, be resolved to ensure the release is fully consistent. Other reviewers should assess these points before final approval.
Update version to 2.2.16 across project files
1 participant
pyproject.toml,uv.lock, and all relevant Dockerfiles for consistency.praisonaiagentsfrom 0.0.88 to 0.0.89.